docs: add T component granularity guidance#173
Open
moss-bryophyta wants to merge 1 commit intomainfrom
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
DX Feedback Loop — Run 3 (2026-03-22)
What triggered this
A naive sub-agent migrating an existing React app to gt-react wasn't sure how granularly to wrap content with
<T>— should each paragraph be wrapped? Each section? The whole page? The docs say "you can wrap as much or as little as you want" but don't give clear guidance on the tradeoffs.What this PR does
Adds a "How much to wrap in a single
<T>" section to the<T>component guide template (which generates docs for both gt-next and gt-react). Includes:Why it matters
This is one of the first decisions developers make after learning about
<T>. Without guidance, some wrap every sentence individually (fragmenting translations) while others wrap too much (making maintenance hard). Clear guidance here prevents both failure modes.